Color profiles |
|
![[Next]](/file/5442/2DAnimationGuide.iso/Software/Animo v3.1 Demo/manual/next.gif){kind=small}
![[Previous]](/file/5442/2DAnimationGuide.iso/Software/Animo v3.1 Demo/manual/prev.gif){kind=small}
![[Up]](/file/5442/2DAnimationGuide.iso/Software/Animo v3.1 Demo/manual/up.gif){kind=small}
![[Top]](/file/5442/2DAnimationGuide.iso/Software/Animo v3.1 Demo/manual/top.gif){kind=small}
![[Contents]](/file/5442/2DAnimationGuide.iso/Software/Animo v3.1 Demo/manual/content.gif){kind=small}
![[Index]](/file/5442/2DAnimationGuide.iso/Software/Animo v3.1 Demo/manual/index.gif){kind=small}
| |
Color space conversion
One thing to be aware of is that when colors are read in they are always converted to the current output color space. This means that if you create some colors in a palette using one monitor, but then load the palette file into an application running on a different host with a different monitor, the colors will be changed to that monitor's color space. If you then save the palette file, the values of the colors stored will be different, even if you didn't change any colors. This shouldn't matter, since if you load the same palette back into an application running on the first host, the colors will be converted back to that host's monitor's color space. However, some colors may not go through this process unchanged. This is because all monitors have a limited gamut (the range of colors that a particular device can represent), so it may be, for example, that a particularly saturated yellow you choose on one monitor cannot be represented on another one. This problem will only occur with colors near the edges of the gamut, which are generally highly saturated colors.
